Cookieless classification of web content

ABSTRACT

In some examples, a system comprises at least one programmable processor; and a machine-readable medium having instructions stored thereon which, when executed by the at least one programmable processor, cause the at least one programmable processor to execute operations comprising: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.

CLAIM OF PRIORITY

This patent application claims the benefit of priority, under 35 U.S.C. Section 119(e), to Rose, U.S. Provisional Patent Application Ser. No. 63/131,303, entitled “WEBSITE CLASSIFICATION USING IN-BROWSER MACHINE LEARNING”, filed on Dec. 28, 2020 (Attorney Docket No. 4525.162PRV), which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

This disclosure relates generally to cookieless web content classification, and in some examples to classifying web pages in order automatically to classify and categorize webpages and, without the use of cookies, relay viewer information to marketers bidding on available inventory on those webpages.

BACKGROUND

Existing technology typically relies on third-party cookies in order to relay information on individuals viewing a website and the details of the content on viewed or other website pages.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter disclosed herein is particularly point out and distinctly claimed in the claims at the conclusion of the specification.

FIG. 1 is a block diagram illustrating a multi-platform integration system in accordance with an example.

FIG. 2 illustrates a computing device in accordance with an example.

FIG. 3 is a flowchart illustrating an exemplary process performed by the multiplatform integration system according to an example.

FIG. 4 is a flowchart illustrating an exemplary process performed the multi-platform integration system according to an example.

DETAILED DESCRIPTION

Described herein are examples of a multi-platform integration system with an adaptive automatic bidding system using script automatically to classify webpages on a website. An example multi-platform integration system includes a computing system in communication with platforms, a database, and one or more user devices in a networked environment. The computing system hosts an application. The computing system is configured to receive a first request from a user device to execute an instance of the application, transmit a graphical user interface (GUI) to the user device to be rendered on a display of the user device, and receive a second request, via the GUI, from the user device to deploy a digital advertisement. In some examples, the second request includes a set of platforms, a set of settings, a set of parameters, and a set of allocation data. The computing system is further configured to interface with each one of the platforms in the set of platforms and integrate the digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data. In some examples, the multi-platform integration system automates and streamlines the advertising trafficking process, resulting in less time trafficking advertising campaigns, fewer human errors and easy advertising budget and performance management. In some examples, a Visto® UI (i.e., the GUI) renders the performance and allows users to spend across all the platforms in a single UI. In some examples, the multi-platform integration system provides operational efficiency, performance enhancement, and an enhanced system to maintain data integrity by reducing human error.

FIG. 1 is a block diagram illustrating a multi-platform integration system in accordance with an example. The multi-platform integration system 100 can include one or more computing systems 150, one or more databases 105, one or more servers 110, one or more user computing devices 130, one or more Demand Side Platforms (DSP) 125A, one or more exchanges 125B, one or more Supply Side Platforms (SSP) 125C, one or more publishers 125D, one or more Application Program Interface (API) programs 125 e, and a Data Management Platform (DMP) 148. In one example, the computing system 150 can be in communication with the database(s) 105, user devices 130, the DSPs 125A, the exchanges 125B, the SSPs 125C, the publishers 125D, the API programs 125 e, a Data Management Platform (DMP) 148, and the [[DMP]] creative libraries database 149, via a communications network 115. The computing system 150 can execute a Visto® application 155. The Visto® application 155 can include the management engine 121 and one or more Application Program Interfaces (APIs) 122. In one example, the management engine 121 can be embodied as a Multi-Platform Ad Management Tool (e.g., a Universal Remote). The computing system 150 can also implement an example of the graphical user interface 123. The management engine 121 can implement the multi-platform integration system 100 using the one or more APIs 122. The Visto® application 155 can reside on one of the computing systems 150 and can be accessible to the user device 130. For example, the user device 130 can execute a web browser or other application and can navigate to a universal resource locator (URL) associated with the Visto® application 155 on the computing system 150, and the user device 130[[0]] can interact with Visto® application 155 via the web browser. Alternatively, at least a portion of the Visto® application 155 can reside on the user device 130 or one of the servers 110.

In some examples, one or more portions of the communications network 115, can include an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless wide area network (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, a wireless network, a WiFi network, a WiMax network, any other type of network, or a combination of two or more such networks.

The computing system 150 may include one or more computers or processors configured to communicate with the database(s) 105, user devices 130, the DSPs 125A, the exchanges 125B, the SSPs 125C, the publishers 125D, the API programs 125 e, and the DMP 148, via the network 115. The computing system 150 may host one or more applications, such as the Visto application 155, configured to interact with one or more components of the user devices 130, the DSPs 125A, the exchanges 125B, the SSPs 125C, the publishers 125D, the API programs 125 e, the DMP 148, and/or facilitates access to the content of the databases 105. The databases 105 may store information/data, as described herein. For example, the databases 105 can include a campaigns database 140, platforms database 145, audience database 147, and a creative libraries database 149. The campaigns database 140 can store information associated with campaigns associated with digital data such as digital advertisements. The platforms database 145 can store information associated with platforms such as media buying platforms. The audience database 147 can include information associate with audience groups for digital advertisement targeting. The creative libraries database 149 can include information associated with creative assets for digital advertisements. The databases 105 can be located at one or more geographically distributed locations from each other or from the computing system 150. Alternatively, the databases 105 can be included within in the computing system 150.

In an example, a user device 130 can execute the Visto® application 155 (e.g., as it resides on the user device 130 or via a web browser) to interface with the computing system 150. In response to executing the Visto® application 155, the computing system 150 can render the GUI 123 on the user device 130. The computing system 150 can receive input from user device 130, via GUI 123.

A user device 130 can transmit a request to integrate digital data along multiple different platforms, via the Visto® application 155, to the computing system 150. In response to receiving the request the computing system 150 can execute the management engine 121. As an example, the digital data can be a digital advertisement. The digital advertisement can be one or more of an image, video, gif, rich text, audio, or other type of digital data. The user can be an entity such as a company, advertiser, educational institution, marketing agency, or governmental institution. The user device 130 can receive a selection of platforms on which the user wishes to distribute the digital advertisement, via the GUI 123 of the Visto® application 155. The platforms can be media buying platforms such as a DSP platform 125A, SSP platform 125B, exchange 125C, publisher 125D, and API programs 125 e. The management engine 121 can receive the selection of platforms, in response to the user device 130 receiving the selection of platforms, via the GUI 123 of the Visto® application 155.

The user device 130 can receive input associated with creating a campaign shell with designated lines, via the GUI 123 of the Visto® application 155. The lines can include placements associated with the campaign. The placements can include attributes such as screens, formats, and targeting. The user device 130 can receive input associated with assigning parameters for the digital advertisement in the Visto® application 155. The parameters can include ad format, screen types, Key Performance Indicators (KPI), etc. The parameters can define the way the advertisement will be delivered. The management engine 121 can receive the input associated with creating a campaign shell with designated lines and the assignment of parameters for the digital advertisement, in response to the user device 130 receiving the input, via the GUI 123 of the Visto® application 155.

The user device 130 can also receive input associated with budget and allocation information, via the GUI 123 of the Visto® application 155. The user device 130 can also receive input associated with a rate and rate type (i.e., type of currency), via the GUI 123 of the Visto® application 155. The rate can be billable cost charged to an advertiser. The user device 130 can also receive input associated with a selection between delivering the digital advertisement based on units or the budget, via the GUI 123 of the Visto® application 155. The management engine 121 can receive the selection of delivering the digital advertisement based on units or budget. In response to inputting a number of units of the digital advertisement a user desires to deliver, the management engine 121 can automatically calculate and render an Ad Budget value, on the GUI 123 of the Visto® application 155. Alternatively, or in addition to, in response to a user inputting an Ad Budget value, the management engine 121 can calculate and/or adjust the number of units of digital advertising to be delivered. The management engine 121 can render the number of units on the GUI 123 of the Visto® application 155.

The user device 130 can also receive input associated with targeting parameters, via the GUI 123 of the Visto® application 155, in order or refine where, when, and to whom the user would like the digital advertisement to be delivered. The user device 130 can also receive input associated with the following targeting parameters: audience, geography, daypart, sellers, and video, white/blacklists. Other parameters are possible.

The audience parameters can be information associated with targeting a focused audience using demographic, behavioral, purchase, search, interest, and other data categories. Audiences are selected from the available data sources such as the audience database 147. For example, the management engine 121 can retrieve the audiences from the audience database 147. The audience database 147 can retrieve audience information from a Data Management Platform (DMP) 148. The DMP 148 can be a centralized data management platform that enables a user to create target audiences based on a combination of first-party and third-party audience data. The audience information can also be retrieved from a selected platform's proprietary segment list.

The geography parameter can include information associated with targeting advertisements based on geographic location. The targeting information can include or exclude geographic regions such as countries, states, metros/Designed Market Areas (DMAs), cities, and zip/postal codes, in which the user would or would not wish to deliver digital advertisements. The daypart parameter can include information associated with delivering digital advertisements based on the days of the week or hours of the day. The user can select the specific days and times on which the user wishes to deliver the digital advertisement.

A seller's parameter can include information associated with targeting a digital advertisement including or excluding specific third-party inventory sellers from open exchange buys. The user can specify the third-party inventory sellers to include or exclude. The video parameter can include information associated with selecting the player size, position, and playback methods on which a digital advertisement will be running. The user can specify the player size, position, and/or playback methods. The white/blacklists parameter can include information associated with including or excluding specific domains or applications in order to control the inventory on which the digital advertisement can be displayed or run. The user can specify the domains or applications to include or exclude.

Some examples may include an in-browser script running on the third-party inventory seller websites to automatically determine the content of the individual webpages in order to relay information to determine desirable or selected content for the available inventory. The management engine 121 can receive the input targeting parameters. The user can select one or more of the aforementioned targeting parameters. Additional targeting parameters can be presented to the user.

The user device 130 can receive input associated with the creative assets of the digital advertisement, via the GUI 123 of the Visto® application 155. The creative assets can include promotional messaging for the user (i.e., advertiser and/or brand). The user can select from two different options to generate the creative assets, add from existing or create new.

The user device 130 receives input associated with a selection of add from existing, via the GUI 123 of the Visto® application 155, the management engine 121 can render a list of creative assets from a creative library on the GUI 123. As an example, the management engine 121 can retrieve a list of creative assets relevant to the user (i.e., advertiser and/or brand) from the creative libraries database 149. The management engine 121 can also render a chosen advertisement format. The management engine 121 can receive the selected creative assets and chose advertisement format based on input from the user device on the GUI 123 of the Visto® application 155.

In some examples, the user device 130 receives input associated with a selection to create new content, from the GUI 123 of the Visto® application 155, the management engine 121 can render an option to create a new creative asset on the GUI 123. The user device 130 can receive input associated with creating new creative asset, via the he GUI 123 of the Visto® application 155. Once a new creative asset is created, the management engine 121 can save the creative asset in a creative library associated with the specific user (user device 130) in the creative libraries database 149.

The management engine 121 can receive the selected creative assets previously created and/or a newly created creative asset. The management engine 121 can render a list of the selected creatives assets including the name, size, an ad server from which the creative asset is hosted (if applicable), and any Secure Sockets Layer (SSL) support on the GUI 123.

In response to completing the selections and input associated with the digital advertisement, the user device 130 can receive a selection to save and close, via the he GUI 123 of the Visto® application 155. The management engine 121 can receive the save and close selection, and save the selected and input information associated with the digital advertisement including selected platforms, parameters, targeting parameters, budget and allocation, and creative assets in the campaigns database 140. The user device 130 can receive a selection to push campaign, via the he GUI 123 of the Visto® application 155. In response to the management engine 121 receiving the selection to push campaign, the management engine 121 can deploy the digital advertisement to the selected platforms. The digital advertisement can be deployed based on the parameters, targeting parameters, budget and allocation, and creative assets. The management engine 121 can use the APIs 122 to interface and integrate the digital advertisement in each of the selected platforms. In response to deploying the digital advertisement, the management engine 121 can render delivery and performance information associated with the digital advertisement for each platform on the GUI 123. The user device 130 can receive input associated with adjustments in the budget and allocation information while the digital advertisement is deployed. In response to the user device 130, receiving a subsequent selection of push campaign, after adjusting the budget and allocation information, the management engine can dynamically reallocate the budget among each of the platforms based on the adjustments and distribute the reallocations to each of the platforms.

As described above, the platforms can be one or more of a DSP 125 a, an exchange 125 b, a SSP 125 c, publishers 125 d, and API programs 125 e. A DSP 125 a can enable buyers with direct real-time bidding access across multiple sources of digital advertisement inventory. The DSP 125 a enables advertisers to purchase impressions (i.e., a view or an ad view), across publisher sites (i.e., publishers 125 d), but targeted to specific users based on information such as their location and their previous browsing behavior. The management engine 121 can deploy the digital advertisement to a DSP 125 a. The management engine 121 can purchase the impressions from publisher sites based on the parameters, targeting parameters, budget and allocation, and creative assets assigned by the user for the digital advertisement.

An exchange 125 b can be an ad exchange. The exchange 125 b can be used by advertisers (i.e., the user) to purchase advertisement space as well as by publishers to sell advertising space. The buying and selling can often be executed using real-time auctions. An exchange 125 b can be a big pool of ad impressions. Publishers 125 d can put their ad impressions into the pool. An advertiser (i.e., the user) can purchase the ad impressions. The purchases can be made in real time based on information such as the previous behavior of the user an ad is being served to, time of day, device type, ad position and more. The management engine 121 can deploy the digital advertisement directly to an exchange 125 b such as an ad exchange. The management engine 121 can purchase ad impressions for the digital advertisements based on the parameters, targeting parameters, budget and allocation, and creative assets for the digital advertisement using the exchange 125 b.

A SSP 125 c can publishers 125 d to sell their inventory to exchanges 125 b and DSP 125 a. The management engine 121 can deploy the digital advertisement directly to the SSP 125 c. The management engine 121 can purchase a publisher's 125 d inventory directly from the SSP 125 c based on the parameters, targeting parameters, budget and allocation, and creative assets for the digital advertisement.

A publisher 125 d can be an entity which publishes (i.e., displays or renders) the digital advertisement. The publisher 125 d can be a website, domain, web application, or any other type of digital media. The publisher 125 d can sell inventory such as ad impressions. Ad impressions can be views, view counts, and/or advertisement space. The management engine 121 can purchase impressions and deploy the digital advertisement directly to on specified publishers 125 d. The management engine 121 can deploy the digital advertisement on the specified publishers 125 d based on parameters, targeting parameters, budget and allocation, and creative assets for the digital advertisement. As a non-limiting example, the digital advertisement can be an image embedded with a hyperlink. The management engine 121 can embed the image of a specified size, with the embedded hyperlink on a publisher's website at a specified location on the website for a specified duration of time. The management engine 121 can indicate which geographic locations the digital advertisement is to be displayed.

An API program 125 e can be custom tools developed enables advertisers and/or agencies (i.e., the user) to publish the digital advertisement with various publishers. As an example, various social media entities can have different API programs to publish the digital advertisements. The management engine 121 can deploy the digital advertisement directly to specified API programs 125 e based on based on parameters, targeting parameters, budget and allocation, and creative assets for the digital advertisement.

In some examples, a digital advertisement can be deployed directly to a DSP 125 a platform, to purchase ad space/impressions for the digital advertisement. The publishers 125 d can interface with the SSP 125 c to sell ad space/impressions. The DSP 125 a and SSP 125 b can interface with one another, via the exchange 125 b.

As described above with respect to FIG. 1, the multi-platform integration system (e.g., multi-platform integration system 100 as shown in FIG. 1) can include a GUI (e.g., GUI 123 as shown in FIG. 1) rendered on a display (e.g., display 131 as shown in FIG. 1) of the user device (e.g., user device 130 as shown in FIG. 1) to facilitate deploying and integrating a digital advertisement on various platforms.

FIG. 2 is a block diagram of an example computing device for implementing some examples. The computing device 200 may be, but is not limited to, a smartphone, laptop, tablet, desktop computer, server, or network appliance. The computing device 200 can be embodied as part of the computing system, user device, platforms (i.e., DSP, exchanges, SSP, publishers, APis), and the DMP. The computing device 200 includes one or more non-transitory computer-readable media for storing one or more computer-executable instructions or software for implementing some examples. The non-transitory computer-readable media may include, but are not limited to, one or more types of hardware memory, non-transitory tangible media (for example, one or more magnetic storage disks, one or more optical disks, one or more flash drives, one or more solid state disks), and the like. For example, memory 206 included in the computing device 200 may store computer-readable and computer-executable instructions or software (e.g., applications 230 such as the Visto® application 155 and management engine 121) for implementing exemplary operations of the computing device 200. The computing device 200 also includes configurable and/or programmable processor 202 and associated core(s) 204, and optionally, one or more additional configurable and/or programmable processor(s) 302′ and associated core(s) 304′ (for example, in the case of computer systems having multiple processors/cores), for executing computer-readable and computer-executable instructions or software stored in the memory 206 and other programs for implementing some examples. Processor 202 and processor(s) 302′ may each be a single core processor or multiple core (204 and 304′) processor. Either or both of processor 202 and processor(s) 302′ may be configured to execute one or more of the instructions described in connection with computing device 200.

Virtualization may be employed in the computing device 200 so that infrastructure and resources in the computing device 200 may be shared dynamically. A virtual machine 212 may be provided to handle a process running on multiple processors so that the process appears to be using only one computing resource rather than multiple computing resources. Multiple virtual machines may also be used with one processor.

Memory 206 may include a computer system memory or random-access memory, such as DRAM, SRAM, EDO RAM, and the like. Memory 206 may include other types of memory as well, or combinations thereof.

A user may interact with the computing device 200 through a visual display device 214, such as a computer monitor, which may display one or more graphical user interfaces 216, multi touch interface 220, and a pointing device 218.

The computing device 200 may also include one or more storage devices 226, such as a hard-drive, CD-ROM, or other computer readable media, for storing data and computer-readable instructions and/or software that implement some examples (e.g., applications i.e., the Visto® application 155). For example, exemplary storage device 226 can include one or more databases 228 for storing information regarding, campaigns, platforms, audiences, and creative libraries. The databases 228 may be updated manually or automatically at any suitable time to add, delete, and/or update one or more data items in the databases.

The computing device 200 can include a network interface 208 configured to interface via one or more network devices 224 with one or more networks, for example, Local Area Network (LAN), Wide Area Network (WAN) or the Internet through a variety of connections including, but not limited to, standard telephone lines, LAN or WAN links (for example, 802.11, T1, T3, 56 kb, X.25), broadband connections (for example, ISDN, Frame Relay, ATM), wireless connections, controller area network (CAN), or some combination of any or all of the above. In some examples, the computing system can include one or more antennas 222 to facilitate wireless communication (e.g., via the network interface) between the computing device 200 and a network and/or between the computing device 200 and other computing devices. The network interface 208 may include a built-in network adapter, network interface card, PCMCIA network card, card bus network adapter, wireless network adapter, USB network adapter, modem, or any other device suitable for interfacing the computing device 200 to any type of network capable of communication and performing the operations described herein.

The computing device 200 may run operating system 210, such as versions of the Microsoft® Windows® operating systems, different releases of the Unix and Linux operating systems, versions of the MacOS® for Macintosh computers, embedded operating systems, real-time operating systems, open-source operating systems, proprietary operating systems, or other operating systems capable of running on the computing device 200 and performing the operations described herein. In some examples, the operating system 210 may be run in native mode or emulated mode. In an example, the operating system 210 may be run on one or more cloud machine instances.

FIG. 3 is a flowchart illustrating an exemplary process performed in the multi-platform integration system. In operation 300, a computing system (i.e., computing system 150 as shown in FIG. 1) hosting an application (i.e., Visto® application 155 as shown in FIG. 1) and in communication with, a plurality of platforms (i.e., the DSP 125 a, exchange 125 b, SSP 125 c, publishers 125 d, and API programs 125 e as shown in FIG. 1), a database (i.e., databases 105 as shown in FIG. 1), and one or more user devices (i.e., user devices 130 as shown in FIG. 1) in a networked environment, can receive a first request from at least one user device from the one or more user devices to execute an instance of the application. In operation 302, the computing system can transmit a graphical user interface (GUI) (i.e., GUI 123 as shown in FIG. 1) to the at least one user device to be rendered on a display of the at least one user device. In operation 304, the computing system can receive a second request, via the GUI, from the at least one user device, to deploy a digital advertisement. The second request includes a set of platforms of the plurality of platforms, a set of settings, a set of parameters, and a set of allocation data. In operation 306, the computing system can interface with each one of the platforms in the set of platforms. In operation 308, the computing system can integrate the digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.

FIG. 4 is a flowchart illustrating exemplary operations in a method. In operation 400, a computing system (i.e., computing system 150 as shown in FIG. 1) hosting an application (i.e., Visto® application 155 as shown in FIG. 1) and in communication with, a plurality of platforms (i.e., the DSP 125 a, exchange 125 b, SSP 125 c, publishers 125 d, and API programs 125 e as shown in FIG. 1), a database (i.e., databases 105 as shown in FIG. 1), and one or more user devices (i.e., user devices 130 as shown in FIG. 1) in a networked environment, can receive a first request from at least one user device from the one or more user devices to execute an instance of the application. In operation 402, the computing system can transmit a graphical user interface (GUI) (i.e., GUI 123 as shown in FIG. 1) to the at least one user device to be rendered on a display of the at least one user device. In operation 404, the computing system can receive a second request, via the GUI, from the at least one user device, to deploy a digital advertisement. The second request includes a set of platforms of the plurality of platforms, a set of settings, a set of parameters, and a set of allocation data. In operation 406, the computing system can interface with each one of the platforms in the set of platforms. In operation 408, the computing system can integrate the digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data. The allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms. In operation 410 the computing system can receive a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms. In operation 412, the computing system can dynamically adjust the allocation data for each of the one of the platforms. In operation 414, the computing system can interface with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on the respective platform, based on the adjustment of the allocation data.

In some examples, the websites have in-browser technology to classify the content and themes of webpages. Using real-time scoring of a webpage will serve to more precisely target and contextualize content to an end-consumer. In some examples, the end consumer or user triggers an instance of a webpage running an in-browser script, the meta data, content, and text of the website is processed through a real-time classification model. The classification model then sends webpage classification to a selected recipient or target destination. The recipient may include an end consumer or user.

In some examples, the scripts crawl all the sub-URL webpages on the websites. That is, the scripts will create a cascading analysis of a website using URL parsing, HTML metadata, and text classification. For example, if CNN content generally includes news item or content, individual pages on CNN may have specific areas of interest such as political, sports, science, weather, business, and the like. Further, these topics may include further categorizations including geographic specifics.

In some examples, webpages are scored in real-time to provide more detailed information in the request to fill available inventory. In some examples, the system is used for real-time dynamic website personalization or DCO content.

Some examples run machine learning scripts on the third-party website browsers to determine the websites content in order to include the information. All data stays on an end-consumer device and is useful for low-latency interference, as well as for privacy preservations.

In some examples, the in-browser script uses machine learning to perform real-time classification of custom webpages and customizations to be categorized. Models can be pre-trained remotely and loaded into browsers. Pre-trained models can be further trained in the browser. In some examples, the machine learning allows for real-time classification of custom webpages and customizations to be categorized. This allows for more granular classification than domain level context that can be received by service providers that classify top level domains. Further, the in-browser learning can parse elements on each page including placement of images, text, comments, and the like. Using machine learning, the script can parse what elements are in images using website metadata and contextual cues. The script can further learn contextual queues to parse what the meaning of the text and the leanings of any comments to the main text.

Some examples can use any form of natural language processing to classify and index the text including semantic distance classification as disclosed in U.S. Pat. No. 9,262,509 which is incorporated by reference herein.

Some examples can use data structures for natural language processing as disclosed in U.S. Pat. Nos. 8,762,382, 7,966,564, 9,262,5409 and United States Patent Publication 2020/0193322 all of which are incorporated by reference herein.

In some examples, a URL crawler differs from a domain crawler chiefly in speed and simplicity of internal implementation of the actual crawler itself. The interfaces (command line, web, and drb) and the data storage schemes may be the same, in some examples. In some examples, a wrapper invokes executable links repeatedly, with a thread-safe queue ensuring that only a fixed number of downloads are running concurrently. Downloads that exceed a specified limit are stopped and the slot is given to a new links process. In some examples, a URL crawler differs from a standard search engine crawler in at least the following ways: an index is not built based on keywords, but based on categories or keyword counts per document. The classification scoring may be more granular than domain level context as used in other services such as Oracle Grapeshot and the like.

Thus, in some examples a computing system comprises: at least one programmable processor; and a machine-readable medium having instructions stored thereon which, when executed by the at least one programmable processor, cause the at least one programmable processor to execute operations comprising: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.

In some examples, the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.

In some examples, the operations further comprise receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.

In some examples, the operations further comprise dynamically adjusting the set of allocation data for each of the one of the platforms.

In some examples, the operations further comprise interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data.

In some examples, a method comprises, at least: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.

In some examples, the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.

In some examples, the method further comprises receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.

In some examples, the method further comprises dynamically adjusting the set of allocation data for each of the one of the platforms.

In some examples, the method further comprises interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data.

In some examples, a non-transitory machine-readable medium comprises instructions which, when read by a machine, cause the machine to perform operations comprising, at least: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.

In some examples, the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.

In some examples, the operations further comprise receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.

In some examples, the operations further comprise dynamically adjusting the set of allocation data for each of the one of the platforms.

In some examples, the operations further comprise interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data.

In describing some examples, specific terminology is used for the sake of clarity. For purposes of description, each specific term is intended to at least include all technical and functional equivalents that operate in a similar manner to accomplish a similar purpose. Additionally, in some instances where a particular example includes a plurality of system elements, device components or method steps, those elements, components, or steps may be replaced with a single element, component, or step. Likewise, a single element, component or step may be replaced with a plurality of elements, components or steps that serve the same purpose. Moreover, while some examples have been shown and described with references to particular examples thereof, those of ordinary skill in the art will understand that various substitutions and alterations in form and detail may be made therein without departing from the scope of the present disclosure. Further still, other aspects, functions, and advantages such as different combinations of the described examples are also within the scope of the present disclosure. 

1. A computing system comprising: at least one programmable processor; and a machine-readable medium having instructions stored thereon which, when executed by the at least one programmable processor, cause the at least one programmable processor to execute operations comprising: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.
 2. The system of claim 1, wherein the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.
 3. The system of claim 2, wherein the operations further comprise receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.
 4. The system of claim 3, wherein the operations further comprise dynamically adjusting the set of allocation data for each of the one of the platforms.
 5. The system of claim 4, wherein the operations further comprise interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data.
 6. A method comprising, at least: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.
 7. The method of claim 5, wherein the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.
 8. The method of claim 7, further comprising receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.
 9. The method of claim 8, further comprising dynamically adjusting the set of allocation data for each of the one of the platforms.
 10. The method of claim 9, further comprising interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data.
 11. A non-transitory machine-readable medium comprising instructions which, when read by a machine, cause the machine to perform operations comprising, at least: receiving a first request from at least one user device to execute an instance of an application; transmitting a graphical user interface (GUI) to the at least one user device to be rendered on a display of the at least one user device; receiving a second request, via the GUI, from the at least one user device, to deploy a digital advertisement, the second request including a set of platforms of a plurality of platforms of a multi-platform integration system, a set of settings, a set of parameters, and a set of allocation data; interfacing with each one of the platforms in the set of platforms; and integrating a digital advertisement directly with each one of the platforms in the set of platforms based on the set of settings, the set of parameters and the set of allocation data.
 12. The medium of claim 11, wherein the set of allocation data is associated with a number of units of the digital advertisement to be deployed to each platform in the set of platforms.
 13. The medium of claim 12, wherein the operations further comprise receiving a third request from the at least one user device to adjust the set of allocation data for one or more platforms of the set of platforms on which the digital advertisement has been integrated, after the digital advertisement is integrated with each one of the platforms of the set of platforms.
 14. The medium of claim 13, wherein the operations further comprise dynamically adjusting the set of allocation data for each of the one of the platforms.
 15. The medium of claim 14, wherein the operations further comprise interfacing with each one of the one or more platforms to adjust the number of units of the digital advertisement to be deployed on a respective platform, based on an adjustment of the set of allocation data. 